Virtualized network function management

ABSTRACT

Briefly, in accordance with one or more embodiments, virtualized network function resources may be managed in a network. Performance measurements may be received for at least one mobility management entity (MME) in an MME pool, or for other network elements. If at least one of the performance measurements exceeds at least one predetermined threshold, instantiation of a new mobility management entity virtual network function (MME VNF) may be requested, and the MME VNF may be instantiated in response to the request. One or more user equipment (UE) devices managed by the MME pool may be connected to the added MME VNF.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. ProvisionalApplication No. 62/034,707 filed Aug. 7, 2014 and the benefit of U.S.Provisional Application No. 62/037,998 filed Aug. 15, 2014. SaidApplication No. 62/034,707 and said Application No. 62/037,998 arehereby incorporated herein by reference in their entireties.

BACKGROUND

In networks operating in accordance with a Third Generation PartnershipProject (3GPP) standard, load balancing and re-balancing of the MobilityManagement Entity (MME) functions may be implemented to ensure that UserEquipment (UE) entering into an MME Pool Area are directed anappropriate MME in a manner such that the UE-MME connections are evenlydistributed among MMEs in the MME pool. Since the number of MMEs in theMME pool is static, an MME can be overloaded as the number of UEsentering the networks keeps rising. Overload control features of the MMEutilize Non-Access Stratum (NAS) signaling to reject NAS requests fromUEs which may result in service degradation to subscribers.

DESCRIPTION OF THE DRAWING FIGURES

Claimed subject matter is particularly pointed out and distinctlyclaimed in the concluding portion of the specification. However, suchsubject matter may be understood by reference to the following detaileddescription when read with the accompanying drawings in which:

FIG. 1 is a diagram of a Mobility Management Entity (MME) virtualizednetwork function (VNF) instantiation and termination in a mixed networkin accordance with one or more embodiments;

FIG. 2 is a diagram of a Mobility Management Entity (MME) virtualizednetwork function (VNF) instance scaling out and in, or up and down, inaccordance with one or more embodiments;

FIG. 3 is a diagram of virtualized network function (VNF) Manager (VNFM)initiated scaling out in accordance with one or more embodiments;

FIG. 4 is a diagram of virtualized network function (VNF) Manager (VNFM)initiated scaling in in accordance with one or more embodiments;

FIG. 5 is a diagram of EM initiated scaling out in accordance with oneor more embodiments;

FIG. 6 is a diagram of EM initiated scaling in in accordance with one ormore embodiments;

FIG. 7 is a block diagram of an information handling system capableimplementing virtualized network management function in accordance withone or more embodiments;

FIG. 8 is an isometric view of an information handling system of FIG. 7that optionally may include a touch screen in accordance with one ormore embodiments; and

FIG. 9 is a diagram of example components of a wireless device such as aUser Equipment (UE) device in accordance with one or more embodiments.

It will be appreciated that for simplicity and/or clarity ofillustration, elements illustrated in the figures have not necessarilybeen drawn to scale. For example, the dimensions of some of the elementsmay be exaggerated relative to other elements for clarity. Further, ifconsidered appropriate, reference numerals have been repeated among thefigures to indicate corresponding and/or analogous elements.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components and/or circuitshave not been described in detail.

In the following description and/or claims, the terms coupled and/orconnected, along with their derivatives, may be used. In particularembodiments, connected may be used to indicate that two or more elementsare in direct physical and/or electrical contact with each other.Coupled may mean that two or more elements are in direct physical and/orelectrical contact. However, coupled may also mean that two or moreelements may not be in direct contact with each other, but yet may stillcooperate and/or interact with each other. For example, “coupled” maymean that two or more elements do not contact each other but areindirectly joined together via another element or intermediate elements.Finally, the terms “on,” “overlying,” and “over” may be used in thefollowing description and claims. “On,” “overlying,” and “over” may beused to indicate that two or more elements are in direct physicalcontact with each other. However, “over” may also mean that two or moreelements are not in direct contact with each other. For example, “over”may mean that one element is above another element but not contact eachother and may have another element or elements in between the twoelements. Furthermore, the term “and/or” may mean “and”, it may mean“or”, it may mean “exclusive-or”, it may mean “one”, it may mean “some,but not all”, it may mean “neither”, and/or it may mean “both”, althoughthe scope of claimed subject matter is not limited in this respect. Inthe following description and/or claims, the terms “comprise” and“include,” along with their derivatives, may be used and are intended assynonyms for each other.

Referring now to FIG. 1 , a diagram of a Mobility Management Entity(MME) virtualized network function (VNF) instantiation and terminationin a mixed network in accordance with one or more embodiments will bediscussed. Although an MME VNF is discussed herein for purposes ofexample, other network elements of network 100 may be implemented as avirtualized network function in addition to an MME, for example aserving gateway (S-GW), packet data network gateway (P-GW), policy andcharging rules function (PCRF), internet protocol multimedia subsystem(IMS), and so on, and the scope of the claimed subject matter is notlimited in this respect. As shown in FIG. 1 , network 100 may include amixed network manager (NM) 110 comprising a legacy network manager (NM)112 and a network functions virtualization (NFV) network manager (NM)114. Mixed network manager 110 provides a package of end-user functionswith the responsibility for the management of network 100 which mayinclude network elements with virtualized network functions, managed byNFV NM 114, and non-virtualized network functions, managed by legacy NM112, as supported by element managers such as element manager (EM) 116and element manager (EM) 118 disposed in respective domain managers,domain manager (DM) 120 and domain manager (DM) 122. In someembodiments, mixed network manager (NM) 110 may also direct access tothe Network Elements of network 100. In one or more embodiments,communication with network 100 may be based at least in part on standardinterfaces and systems supporting multi-technology Network Elements,although the scope of the claimed subject matter is not limited in thisrespect.

In one or more embodiments, network 100 may operate in compliance with aThird Generation Partnership Project (3GPP) standard to provide a 3GPPSA5 management framework and with European Telecommunication StandardsInstitute (ETSI) standard such as network functions virtualization (NVF)Management and Orchestration (MANO) standard to support lifecyclemanagement to instantiate, terminate, scale in, scale out, scale up,and/or scale down one or more virtualized network function (VNF)instances dynamically according to demand and/or for load balancing. Asdiscussed herein, instantiation means starting or running a virtualmachine that is capable of implementing a virtualized network function(VNF) such as a VNF for a mobility management entity (MME) of network100, and termination means to close or to stop running such a virtualmachine. As discussed herein, scaling out means adding or running one ormore additional virtual machines capable of implementing a VNF inaddition to one or more virtual machines already operating on network100, that is increasing the number of virtual machines running onnetwork 100, and scaling in means removing or stopping running one ormore such virtual machines, that is reducing the number of virtualmachine running network 100. As discussed herein, scaling up meansadding one or more hardware resources, such as computing, memory,storage, and/or networking resources to support one or more virtualmachines running on network 100, and scaling down means removing one ormore such hardware resources from supporting one or more virtualmachines running on network 100. These are merely example definitions,however, and other variations or definitions likewise may be provided asdiscussed herein and/or as understood by one of skill in the art, andthe scope of the claimed subject matter is not limited in theserespects.

As shown in FIG. 1 , a mobility management entity (MME) virtualizednetwork function (VNF) 124 may be instantiated or terminated in network100 using mixed network NM 110 where a non-virtualized MME NetworkElement (MME NE) may be collocated in the same MME pool as MME VNF, forexample before networks that implement NVF are fully deployed. As shownin FIG. 1 , MME VNF 124 may be instantiated in network 100 where anon-virtualized MME, MME NE 126, is collocated with MME VNF 124 andaligned with VNF instantiation flow, for example in accordance with aEuropean Telecommunication Standards Institute (ETSI) standard such asnetwork functions virtualization (NVF) Management and Orchestration(MANO), although the scope of the claimed subject matter is not limitedin this respect. In such an arrangement, following actions may beperformed. It is noted that one particular order and number of actionsdescribed below are discussed for purposes of example, but other ordersand numbers of actions may be implemented, and the scope of the claimedsubject matter is not limited in these respects. Legacy NM 112 of mixednetwork MN 110 receives the measurements of MME processor usage andS1-MME data volume, for example according to a 3GPP specification, ofthe non-virtualized MME, MME NE 126, from EM 116. It is noted that MMENE 126 may be managing one or more evolved Node B (eNB) networkelements, such as eNB 128, eNB 130, and/or eNB 132, which in turn may beserving one or more user equipment (UE) network elements (not shown),which may present the measured MME processor usage and S1-MME datavolume to MME NE 126 based on the usage and loading from the variouseNBs and/or UEs. Mixed network NM 110 sends a request to NVForchestrator (NFVO) 134 to instantiate a new MME VNF, such as MME VNG124, when mixed network NM 110 detects that the MME processor usage orS1-MME data volume counters are above one or more predeterminedthresholds. In an alternative embodiment, mixed network NM 110 mayforward the measurements to NFVO 134 and let NFVO 134 make the decisionon when a new MME VNF should be instantiated.

In one or more embodiments, NFVO 134, VNF Manager 136, and VirtualizedInfrastructure Manager (VIM) 138 may be part of NFV Management andOrchestration (NFV-MANO) 140 in accordance with an ETSI standard,although the scope of the claimed subject matter is not limited in thisrespect. In such embodiments, VIM 138 may couple to NFV Infrastructure(NFVI) 142 which comprises Network Element physical hardware 144 andVirtualization Layer 146. Network Element physical hardware 144 maycomprise compute and/or processing hardware, storage hardware, and/ornetworking hardware, for example realized by one or more commercial offthe shelf (COTS) servers or the like. Virtualization layer 146 maycomprise virtualization software running on Network Element physicalhardware 144, for example virtual machine management software and/orhypervisor software. MME VNF 124 may comprise software or instructionsrunning on Network Element physical hardware 144 that is managed byvirtualization layer 146. It should be noted that these are merelyexample implementations of NFVI 142 and MME VNF 124, and the scope ofthe claimed subject matter is not limited in these respects.

NFVO 134 validates the request by checking sender authorization and/orinstantiation parameters, and may run a feasibility check. If therequest is validated successfully, NFVO 134 calls VNF manager (VNFM) 135to instantiate MME VNF 124. VNFM 136 validates the request and processesthe instantiation parameters. VNFM 136 then sends a request to NFVO 134for resource allocation. NFVO 134 executes any needed resourcepre-allocation, and then sends a request to virtualized infrastructuremanager (VIM) 138 for resource allocation. For example, if MME processorusage counter is above a predetermined threshold, VIM 138 allocates morecomputing and storage resources. If the S1-MME data volume counter isabove a predetermined threshold, VIM 138 allocates more networkingcapacity.

In response to a request for resource allocation, VIM 138 allocates therequested computing, storage and/or networking resources, and sends anacknowledgement to NFVO 134. NFVO 134 sends an acknowledgement to VNFM136 to indicate the completion of resource allocation. VNFM 136 theninstantiates MME VNF 124, and configures MME VNF 124 with any MME VNFspecific lifecycle parameters. VNFM 136 notifies EM 118 of new MME VNF124. EM 118 then configures MME VNF 136 with information required forMME operation. VNFM 136 acknowledges the completion of instantiation ofMME VNF 124 back to NFVO 134. NFVO 134 acknowledges the completion ofinstantiation of MME VNF 124 to mixed network NM 110. Mixed network NM110 configures EM 116 of non-virtualized MME, MME NE 126, and EM 118 ofMME VNF 124, by adding new MME VNF 124 to the MME pool, and informingMME NE 126 about the new MME VNF 124. MME NE 26 then will offload UEs inthe ECM-CONNECTED mode to MME VNF 124 by initiating an S1 Releaseprocedure with release cause “load balancing TAU required”, for exampleaccording to a 3GPP specification, that will request the UE to performtracking area update to connect to MME VNF 124, although the scope ofthe claimed subject matter is not limited in this respect.

In one or more embodiments, MME VNF 124 may be terminated in a mixednetwork, network 100 of FIG. 1 , and may be aligned with VNF instancetermination in NFV MANO 140 by implementing the following processes.Mixed network NM 110 receives the measurements of MME processor usageand data volume counters of non-virtualized MME, MME NE 126, and MME VNF124 from EM 116 and EM 118. Mixed network NM 110 determines that MME VNF124 may be terminated from analyzing the MME processor usage or datavolume measurements of both MME NE 126 and MME VNF 124, and sends arequest to NFVO 134 to initiate termination of MME VNF 124. In analternative embodiment, mixed network NM 110 may forward themeasurements to NFVO 134 and let NFVO 134 make the decision on when MMEVNF 124 should be terminated. NFVO 134 validates the request by checkingsender authorization, and verifying the existence of the instance of MMEVNF 124. If the request is validated successfully, NFVO 134 will callVNFM 136 to terminate the instance of MME VNF 124. VNFM 136 sends arequest to MME VNF 124 to terminate the VNF instance. In response, MMEVNF 124 offload UEs in the ECM-CONNECTED mode to MME NE 126 byinitiating the S1 Release procedure with release cause “load balancingTAU required” that will request the UE to perform tracking area updateto connect to MME NE 126. After all UEs are offloaded to MME NE 126, MMEVNF 124 sends a notification to VNFM 136 to indicate that the MME VNFinstance has been terminated. VNFM 136 sends an acknowledgement to NFVOto indicate the completion of termination of the instance of MME VNF136. NFVO 134 sends a request to VIM 138 to release the resources. VIM138 deletes the networking, computing, and/or storage resources, andsends an acknowledgement to NFVO 134 to indicate the completion ofresource de-allocation. NFVO 134 acknowledges the completion of MME VNFinstance termination to mixed network NM 110. Mixed network NM 110configures EM 116 of MME NE 126 and EM 118 of MME VNF 124 that the MMEVNF instance has been terminated.

Referring now to FIG. 2 , a diagram of a Mobility Management Entity(MME) virtualized network function (VNF) instance scaling out and in, orup and down, in accordance with one or more embodiments will bediscussed. The embodiment shown in FIG. 2 illustrates how an instance ofmobility management entity virtualized network function (MME VNF) 124can be scaled out when network functions virtualization network manager(NFV NM) 114 detects that the instance of MME VNF 124 is overloaded viathe threshold crossing events, for example MME VNF processor usage ordata volume counters, and is aligned with VNF instance scaling flow inETSI NFV-MANO 140. To minimize the impacts to the existing 3GPPmanagement frameworks, in such an embodiment it may be assumed that theinstance of MME VNF 124 scaling is triggered when NFV NM 114 detectsthat VNF processor usage or data volume counters are above one or morepredetermined thresholds.

In one or more embodiments, scaling out of an instance of MME VNF 124may be as follows. A first instance, MME VNF (instance 1) 124, may embeda monitor function to measure VNF performance and sends the measurementsto element manager (EM) 116. EM 116 receives the measurements, such asMME VNF processor usage and/or data volume counters, and converts themeasurements into the Type-2 message format that are sent to NFV NM 114.NFV NM 114 sends a request to NFVO 134 to scale out a new MME VNFinstance, for MME VNF (instance 2) 212, when NFV NM 114 detects that themeasurements are above one or more predetermined thresholds. In analternative embodiment, NFV NM 114 may decide to forward themeasurements to NFVO 134 and let NFVO 134 make the decision on when toscale out an MME VNF instance. NFVO 134 validates the request againstpolicy conformance. If the request is validated successfully, NFVO 134sends the scaling out request to VNFM 136. VNFM 136 executes anyinvolved preparation work, and then sends a request to NFVO 134 toallocate resources to support the new MME VNF instance, MME VNF(instance 2) 212. NFVO 134 executes any needed resource pre-allocation,and then sends a request to VIM 138 for resource allocation. VIM 138allocates the requested computing, storage and/or networking resources,and sends an acknowledgement to NFVO 134. NFVO 134 sends anacknowledgement to VNFM 136 to indicate the completion of resourceallocation.

VNFM 136 instantiates MME VNF (instance 2) 212, and configures MME VNF(instance 2) with any MME VNF specific lifecycle parameters. VNFM 136notifies EM 116 of the new MME VNF (instance 2) 212. EM 116 thenconfigures the MME VNF (instance 2) 212 with information required forMME VNF instance operation. VNFM 136 acknowledges NFVO 134 that theinstantiation of MME VNF (instance 2) 212 has been completed. NFVO 134acknowledges NFV NM 134 that the instantiation of MME VNF (instance 2)212 has been completed. NFV NM 134 configures EM 116 by adding the newMME VNF (instance 2) 212 to the MME pool, and informing MME VNF(instance 1) 124 about the new the MME VNF (instance 2) 212. MME VNF(instance 1) 124 will offload UEs in the ECM-CONNECTED mode to MME VNF(instance 2) 212 by initiating the S1 Release procedure with releasecause “load balancing TAU required” that will request the UE to performtracking area update to connect to the MME VNF (instance 2) 212.

In another embodiment, a MME VNF instance may be scaled in when NFV NM114 detects that MME VNF instances are not overloaded via thenotification of threshold crossing events, for example MME VNF processorusage and/or data volume counters, and is aligned with the VNF instancescaling flow in ETSI NFV-MANO 140. A process for MME VNF instancescaling in may be as follows. MME VNF (instance 1) 124 and MME VNF(instance 2) 212 may embed a monitor function to measure the VNFperformance and send the measurements to EM 116. EM 116 receives themeasurements such as MME VNF processor usage and/or data volumecounters, and converts the measurements into the Type-2 message formatthat are sent to NFV NM 114. NFV NM 114 sends a request to NFVO 134 toscale in MME VNF (instance 2) 212 when it detects that the measurementsare below one or more predetermined thresholds, and a single MME VNFinstance is capable of supporting the UEs of network 100. In analternative embodiment, NFV NM 114 may forward the measurements to NFVO134 and let NFVO 134 make the decision on when to scale in a MME VNF.NFVO 134 validates the request against policy conformance. If therequest is validated successfully, NFVO 134 sends the scaling in requestto VNFM 136. VNFM 136 sends a request to MME VNF (instance 2) 212 toremove MME VNF (instance 2) 212. MME VNF (instance 2) 212 offloads UEsin the ECM-CONNECTED mode to MME VNF (instance 1) 124 by initiating theS1 Release procedure with release cause “load balancing TAU required”that will request the UE to perform tracking area update to connect toMME VNF (instance 1) 124. MME VNF (instance 2) 212 detects that all UEsare offloaded to MME VNF (instance 1) 124, and sends a notification toVNFM 136 to indicate that the MME VNF (instance 2) 212 has been removed.VNFM 136 sends an acknowledgement to NFVO 134 to indicate the completionof removal of MME VNF (instance 2) 212. NFVO 134 sends a request to VIM138 to release the resources associated with MME VNF (instance 2) 212.VIM 138 deletes the network connections, computing, and/or storageresources, and sends an acknowledgement to NFVO 134 to indicate thecompletion of resource de-allocation. NFVO 134 acknowledges thecompletion of removal of MME VNF (instance 2) 212 to NFV NM 114. NFV NM114 configures EM 116 that MME VNF (instance 2) 212 has been terminated.

In one or more embodiments, an MME VNF instance may scale up and downthe resources according to the need of a MME VNF to serve UE connectingto networks 100. Such an arrangement is aligned with the VNF instancescaling flow in ETSI NFV-MANO 140. To minimize the impacts to theexisting 3GPP management frameworks, in one or more embodiments the MMEVNF instance scaling may be triggered when NFV NM 114 detects that VNFprocessor usage and/or data volume counters are above or belowpredetermined thresholds. A process for MME VNF instance scaling up anddown may be as follows. MME VNF 124 embeds a monitor function to measurethe VNF performance, and then sends the measurements to EM 116. EM 116receives the VNF measurements, for example MME VNF processor usageand/or data volume counters, and converts them into Type-2 messageformat that are sent to NFV NM 114. NFV NM 114 sends a request to NFVO134 to scale up or scale down the VNF resources when NFV NM 114 detectsthe measurements are above or below one or more predeterminedthresholds, respectively. In an alternative embodiment, NFV NM 114 maydecide to forward the measurements to NFVO 134 and let NFVO 134 make thedecision on when to scale up or down an MME VNF such as MME VNF(instance 1) 124. NFVO 134 validates the request against policyconformance. If the request is validated successfully, NFVO 134 sendsthe scaling request to VNFM 136. VNFM 136 executes any neededpreparation work, then sends a request to NFVO 134 for resourceallocation. NFVO 134 sends a request to VIM 138 to allocate or release.For example, if the measurements are above a predetermined threshold,VIM 138 increases networking, computing and/or storage resources. If themeasurements are below a predetermined threshold, VIM 138 will reducenetworking, computing and/or storage resources. The thresholds should beset properly to prevent a ping-pong effect of scaling up and down whenat or near a threshold. For example, a threshold to increase resourcesmay have a different value tan the threshold to decrease resources,although the scope of the claimed subject matter is not limited in thisrespect.

VIM 138 increases or reduces the networking, computing, and storageresources of MME VNF 124, according to the scaling up or down request,respectively, and sends an acknowledgement to NFVO 134. NFVO 134 sendsan acknowledgement to VNFM 136 to indicate the completion of resourcesadjustment. VNFM 136 configures MME VNF 124 according to the scalingrequest. VNFM 136 acknowledges the completion of MME VNF instancescaling up/down back to NFVO 134. NFVO 134 acknowledges the completionof MME VNF instance scaling up/down to NFV NM 114. NFV NM 114 configuresEM 116 with the adjusted resources for MME VNF 124. MME VNF 124 willupdate all eNBs such as eNB 128, eNB 130, and/or eNB 132, which areconnected to MME VNF 124 with the new weight factor according to theadjusted resources, via “Relative MME Capacity” IE in “MME CONFIGURATIONUPDATE” message, for example according to a 3GPP specification, althoughthe scope of the claimed subject matter is not limited in this respect.

Referring now to FIG. 3 , a diagram of virtualized network function(VNF) Manager (VNFM) initiated scaling out in accordance with one ormore embodiments will be discussed. As shown in FIG. 1 , MME VNF(instance 1) 124 may embed a monitor function to measure the VNFperformance metrics, and send the measurements, for example MME VNFprocessor usage and/or data volume counter, to VNFM 136. VNFM 138detects that the MME processor usage and/or volume counters are aboveone or more predetermined thresholds, and there is shortage of resourcesfor which expansion may address the shortage. Based on the parametersprovided in the VNF descriptor, for example memory parameters, computingparameters, and so on, VNFM 138 requests NFVO 134 permission forexpansion. In an alternative embodiment, VNFM 138 may decide to forwardthe measurements to NFVO 134 and let NFVO 134 make the decision on whento scale out an instance of MME VNF. NFVO 134 checks for free resourcesagainst its database. If resources are available, NFVO 134 sends out anoptional resource reservation request to VIM 138, and VIM 138 allocatesthe requested computing, storage and/or networking resources, and sendsan acknowledgement to NFVO 134. NFVO 134 sends an acknowledgement toVNFM 136 to indicate the completion of resource allocation. VNFM 136requests VIM 138 to start one or more virtual machines (VMs) asindicated by NFVO 134, for example VIM Identifiers, parameters for thevirtual machines, and so on. VIM 138 acknowledges successfully runningthe VMs and other network resources. VNFM 136 instantiates the MME VNF(instance 2) 212, and configures MME VNF (instance 2) 212 with any MMEVNF specific lifecycle parameters. VNFM 136 notifies EM 116 of the newMME instance, MME VNF (instance 2) 212. EM 212 then configures the MMEVNF (instance 2) 212 with information required for MME VNF instanceoperation. VNFM 136 reports successful addition of a new MME VNFinstance to NFVO 134. NFVO 134 updates its database with the new MMEinstance descriptor. EM 116 notifies NFV NM 114 of the new MME VNF(instance 2) 212. NFV NM 114 acknowledges the successful instantiationof the new MME VNF (instance 2) 212. EM 116 configures the MME VNF(instance 2) 212 with any application specific parameters. EM 116notifies MME (instance 1) 124 about the new MME instance, MME VNF(instance 2) 212, added in the MME pool. MME VNF (instance 1) 124 willoffload UEs in the ECM-CONNECTED mode to MME VNF (instance 2) 212 byinitiating the S1 Release procedure with release cause “load balancingTAU required” that will request UEs connected to network 100 to performtracking area update to connect to the MME VNF (instance 2) 212.

Referring now to FIG. 4 , a diagram of virtualized network function(VNF) Manager (VNFM) initiated scaling in in accordance with one or moreembodiments will be discussed. FIG. 4 illustrates how an MME VNFinstance may be scaled in when VNFM 136 detects that the MME VNFinstance is not sufficiently loaded to match the threshold crossingevents, for example MME VNF processor usage and/or data volume counters,and is aligned with VNF instance scaling flow in ETSI NFV-MANO 140. Theinformation involved to detect a need for scaling may be provided in theVNF descriptor. A process of VNFM 136 initiated scaling in may be asfollows. MME VNF instances, MME VNF (instance 1) 124 and MME VNF(instance 2), may embed a monitor function to measure the VNFperformance metrics, and send the measurements such as MME VNF processorusage and/or data volume counters to VNFM 136. VNFM 136 detects that theMME processor usage or data volume counters are below one or morepredetermined thresholds, and there is a capacity to release resourceswhich may allow scaling in/release of resources. Based on the parametersprovided in the VNF descriptor, for example memory, computing, and soon, VNFM 136 requests NFVO 134 permission for scaling in. In analternative embodiment, VNFM 136 may forward the measurements to NFVO134, and NFVO 134 makes the decision on when to scale in a MME VNF. NFVO134 checks for resources against its database, and grants the scaling inoperation to VNFM 136. VNFM 136 sends a request to MME VNF (instance 2)212 to remove the MME VNF instance. MME VNF (instance 2) 212 willoffload UEs in the ECM-CONNECTED mode to MME VNF (instance 1) 124 byinitiating the S1 Release procedure with release cause “load balancingTAU required” that will request the UEs to perform tracking area updateto connect to MME VNF (instance 1) 124. After the UEs are offloaded toVNF (instance 1) 124 from VNF (instance 2) 212, VNF (instance 2) 212sends a notification to indicate VNF (instance 2) 212 has been removed.After MME VNF (instance 2) 212 is completely shut down, VNFM 136requests VIM 138 to delete all the associated resources. VIM 138acknowledges removal of all the resources associated with the MME VNF(instance 2) 212. VNFM 136 reports successful completion ofcontraction/scaling in to NFVO 134. NFVO 134 updates its database toreflect the change. VNFM 136 notifies EM 116 on the removal of MME VNF(instance 2) 212. EM 116 in turn notifies NFV NM 114 of the removal ofMME VNF (instance 2) 212. NFV NM 114 then acknowledges the changes.

Referring now to FIG. 5 , a diagram of element manager (EM) initiatedscaling out in accordance with one or more embodiments will bediscussed. FIG. 5 illustrates how an MME VNF instance may be scaled outwhen EM 116 detects that MME VNF (instance 1) 124 is overloaded viathreshold crossing events, for example MME VNF processor usage and/ordata volume counters, and is aligned with VNF instance scaling flow inETSI NFV-MANO 140. EM 116 monitors the performance metrics and thresholddetection if not supported in the MME VNF. In this case, the decision toscale may be taken at EM 116 and forwarded to VNFM 136. A process for EMinitiated scaling out may be as follows. EM 116 receives performancemeasurements, for example MME VNF processor usage and/or data volumecounters, from MME VNF (instance 1) 124. EM 116 detects that the MMEprocessor usage and/or data volume counters are above one or morepredetermined thresholds, and requests the scale out operation to VNFM136. The decision to scale may be taken by EM 116 based on theperformance metrics monitored. In an alternative embodiment, EM 116 mayforward the measurements VNFM 136 which in turn sends the measurementsto NFVO 134, and NFVO 134 makes the decision on when to scale out MMEVNF to a new instance, and then request VNFM 136 to scale out a newinstance. Based on the parameters provided in the VNF descriptor, suchas memory, computing, and so on, VNFM 136 requests NFVO 134 permissionfor expansion. NFVO 134 checks for free resources against its database.NFVO 134 sends out an optional resource reservation request to VIM 138,and VIM 138 allocates the requested computing, storage and/or networkingresources, and sends an acknowledgement to NFVO 134. NFVO 134 sends anacknowledgement to VNFM 136 to indicate the completion of resourceallocation. VNFM 136 requests VIM 138 to start one or more virtualmachines (VMs) as indicated by NFVO 134 for example using VIMIdentifiers, virtual machine parameters, and so on. VIM 138 acknowledgessuccessfully running the virtual machines and other network resources.VNFM 136 instantiates MME VNF (instance 2) 212, and configures MME VNF(instance 2) 212 with any MME VNF specific lifecycle parameters. VNFM136 acknowledges to EM 116 of new MME VNF (instance 2) 212. EM 116 thenconfigures MME VNF (instance 2) 212 with information involved for MMEVNF instance operation. VNFM 126 reports successful addition of a newMME VNF instance, MME VNF (instance 2) 212, to NFVO 134. NFVO 134updates its database with the new MME instance descriptor. EM 116notifies NFV NM 114 of new MME VNF (instance 2) 212. NFV NM 114acknowledges the successful instantiation of new MME VNF (instance 2)212. EM 116 configures MME VNF (instance 2) 212 with any applicationspecific parameters. EM 116 notifies MME VNF (instance 1) 124 about newMME VNF (instance 2) 212 added in the MME pool. MME VNF (instance 1) 124will offload one or more UEs in the ECM-CONNECTED mode to MME VNF(instance 2) 212 by initiating the S1 Release procedure with releasecause “load balancing TAU required” that will request the UEs to performtracking area update to connect to MME VNF (instance 2) 212.

Referring now to FIG. 6 , a diagram of element manager (EM) initiatedscaling in in accordance with one or more embodiments will be discussed.FIG. 6 illustrates how an MME VNF instance can be scaled in when EM 116detects that MME VNF (instance 2) 212 is not sufficiently loaded tomatch the threshold crossing events, for example MME VNF processor usageand/or data volume counters, and is aligned with VNF instance scalingflow in ETSI NFV-MANO 140. EM 116 monitors the performance metrics andthreshold detection. In this case, the decision to scale is taken at EM116 and forwarded to the VNFM 136. A process of EM initiated scaling inmay be as follows. EM 116 monitors the performance metrics, for exampleMME VNF processor usage and/or data volume counters, and reports sentfrom the MME VNF instances MME VNF (instance 1) 124 and/or MME VNF(instance 2) 212, and makes a decision involved for scaling. EM 116detects that the MME processor usage or data volume counters are belowpredetermined thresholds, and there and there is a capacity to releaseresources which may allow scaling in (release) of resources. EM 116requests the scale in operation to VNFM 136. In an alternativeembodiment, EM 116 may forward the measurements VNFM 136 which in turnsends the measurements to NFVO 134, and NFVO 134 makes the decision onwhen to scale in a MME VNF. Based on the parameters provided in the VNFdescriptor, for example memory, computing, and so on, VNFM 136 requestsNFVO 134 permission for scaling in. NFVO 134 checks for resourcesagainst its database, and NFVO 134 grants the scaling in operation toVNFM 136. VNFM 136 sends a request to MME VNF (instance 2) 212 to removethe MME VNF instance. MME VNF (instance 2) 212 will offload one or moreUEs in the ECM-CONNECTED mode to MME VNF (instance 1) 124 by initiatingthe S1 Release procedure with release cause “load balancing TAUrequired” that will request the UE to perform tracking area update toconnect to the MME VNF (instance 2) 124. After the UEs are offloaded toMME VNF (instance 1) 124 from MME VNF (instance 2) 212, MME VNF(instance 2) 212 sends a notification to indicate VNF (instance 2) 212has been removed. Once MME VNF (instance 2) 212 is completely shut down,VNFM 136 requests VIM 138 to delete all the associated resources. VIM138 acknowledges removal of all the resources associated with the MMEVNF (instance 2) 212. VNFM 136 reports successful completion ofcontraction (scaling in) to NFVO 134. NFVO 134 updates its data base toreflect the change. VNFM 136 acknowledges EM 116 on the removal of MMEVNF (instance 2) 212. EM 116 in turn notifies NFV NM 114 of the removalof MME VNF (instance 2) 212, and NFV NM 114 acknowledges the changes.

Referring now to FIG. 7 , a block diagram of an information handlingsystem capable of implementing virtualized network function managementaccordance with one or more embodiments will be discussed. Informationhandling system 700 of FIG. 7 may tangibly embody any one or more of theelements described herein, above, including for example mixed network NM110, DM 120, DM 122, NFVI 142, MME 126, eNB 18, eNB 130, eNB 132, and/orNFV-MANO 140, with greater or fewer components depending on the hardwarespecifications of the particular device. Although information handlingsystem 700 represents one example of several types of computingplatforms, information handling system 700 may include more or fewerelements and/or different arrangements of elements than shown in FIG. 7, and the scope of the claimed subject matter is not limited in theserespects.

In one or more embodiments, information handling system 700 may includean application processor 710 and a baseband processor 712. Applicationprocessor 710 may be utilized as a general-purpose processor to runapplications and the various subsystems for information handling system700. Application processor 710 may include a single core oralternatively may include multiple processing cores wherein one or moreof the cores may comprise a digital signal processor or digital signalprocessing (DSP) core. Furthermore, application processor 710 mayinclude a graphics processor or coprocessor disposed on the same chip,or alternatively a graphics processor coupled to application processor710 may comprise a separate, discrete graphics chip. Applicationprocessor 710 may include on board memory such as cache memory, andfurther may be coupled to external memory devices such as synchronousdynamic random access memory (SDRAM) 714 for storing and/or executingapplications during operation, and NAND flash 716 for storingapplications and/or data even when information handling system 700 ispowered off. In one or more embodiments, instructions to operate orconfigure the information handling system 1100 and/or any of itscomponents or subsystems to operate in a manner as described herein maybe stored on a article of manufacture comprising a non-transitorystorage medium. In one or more embodiments, the storage medium maycomprise any of the memory devices shown in and described herein,although the scope of the claimed subject matter is not limited in thisrespect. Baseband processor 712 may control the broadband radiofunctions for information handling system 700. Baseband processor 712may store code for controlling such broadband radio functions in a NORflash 718. Baseband processor 712 controls a wireless wide area network(WWAN) transceiver 720 which is used for modulating and/or demodulatingbroadband network signals, for example for communicating via a 3GPP LTEor LTE-Advanced network or the like.

In general, WWAN transceiver 720 may operate according to any one ormore of the following radio communication technologies and/or standardsincluding but not limited to: a Global System for Mobile Communications(GSM) radio communication technology, a General Packet Radio Service(GPRS) radio communication technology, an Enhanced Data Rates for GSMEvolution (EDGE) radio communication technology, and/or a ThirdGeneration Partnership Project (3GPP) radio communication technology,for example Universal Mobile Telecommunications System (UMTS), Freedomof Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP LongTerm Evolution Advanced (LTE Advanced), Code division multiple access2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, ThirdGeneration (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDMA (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), UMTS Terrestrial RadioAccess (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long TermEvolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G),Code division multiple access 2000 (Third generation) (CDMA2000 (3G)),Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced MobilePhone System (1st Generation) (AMPS (1G)), Total Access CommunicationSystem/Extended Total Access Communication System (TACS/ETACS), DigitalAMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), MobileTelephone System (MTS), Improved Mobile Telephone System (IMTS),Advanced Mobile Telephone System (AMTS), OLT (Norwegian for OffentligLandmobil Telefoni, Public Land Mobile Telephony), MTD (Swedishabbreviation for Mobiltelefonisystem D, or Mobile telephony system D),Public Automated Land Mobile (Autotel/PALM), ARP (Finnish forAutoradiopuhelin, “car radio phone”), NMT (Nordic Mobile Telephony),High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap),Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, IntegratedDigital Enhanced Network (iDEN), Personal Digital Cellular (PDC),Circuit Switched Data (CSD), Personal Handy-phone System (PHS), WidebandIntegrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed MobileAccess (UMA), also referred to as also referred to as 3GPP GenericAccess Network, or GAN standard), Zigbee, Bluetooth®, and/or generaltelemetry transceivers, and in general any type of RF circuit or RFIsensitive circuit. It should be noted that such standards may evolveover time, and/or new standards may be promulgated, and the scope of theclaimed subject matter is not limited in this respect.

The WWAN transceiver 720 couples to one or more power amps 742respectively coupled to one or more antennas 724 for sending andreceiving radio-frequency signals via the WWAN broadband network. Thebaseband processor 712 also may control a wireless local area network(WLAN) transceiver 726 coupled to one or more suitable antennas 728 andwhich may be capable of communicating via a Wi-Fi, Bluetooth®, and/or anamplitude modulation (AM) or frequency modulation (FM) radio standardincluding an IEEE 802.11 a/b/g/n standard or the like. It should benoted that these are merely example implementations for applicationprocessor 710 and baseband processor 712, and the scope of the claimedsubject matter is not limited in these respects. For example, any one ormore of SDRAM 714, NAND flash 716 and/or NOR flash 718 may compriseother types of memory technology such as magnetic memory, chalcogenidememory, phase change memory, or ovonic memory, and the scope of theclaimed subject matter is not limited in this respect.

In one or more embodiments, application processor 710 may drive adisplay 730 for displaying various information or data, and may furtherreceive touch input from a user via a touch screen 732 for example via afinger or a stylus. An ambient light sensor 734 may be utilized todetect an amount of ambient light in which information handling system700 is operating, for example to control a brightness or contrast valuefor display 730 as a function of the intensity of ambient light detectedby ambient light sensor 734. One or more cameras 736 may be utilized tocapture images that are processed by application processor 710 and/or atleast temporarily stored in NAND flash 716. Furthermore, applicationprocessor may couple to a gyroscope 738, accelerometer 740, magnetometer742, audio coder/decoder (CODEC) 744, and/or global positioning system(GPS) controller 746 coupled to an appropriate GPS antenna 748, fordetection of various environmental properties including location,movement, and/or orientation of information handling system 700.Alternatively, controller 746 may comprise a Global Navigation SatelliteSystem (GNSS) controller. Audio CODEC 744 may be coupled to one or moreaudio ports 750 to provide microphone input and speaker outputs eithervia internal devices and/or via external devices coupled to informationhandling system via the audio ports 750, for example via a headphone andmicrophone jack. In addition, application processor 710 may couple toone or more input/output (I/O) transceivers 752 to couple to one or moreI/O ports 754 such as a universal serial bus (USB) port, ahigh-definition multimedia interface (HDMI) port, a serial port, and soon. Furthermore, one or more of the I/O transceivers 752 may couple toone or more memory slots 756 for optional removable memory such assecure digital (SD) card or a subscriber identity module (SIM) card,although the scope of the claimed subject matter is not limited in theserespects.

Referring now to FIG. 8 , an isometric view of an information handlingsystem of FIG. 7 that optionally may include a touch screen inaccordance with one or more embodiments will be discussed. FIG. 8 showsan example implementation of information handling system 1100 of FIG. 7tangibly embodied as a cellular telephone, smartphone, or tablet typedevice or the like. The information handling system 700 may comprise ahousing 810 having a display 730 which may include a touch screen 732for receiving tactile input control and commands via a finger 816 of auser and/or a via stylus 1218 to control one or more applicationprocessors 710. The housing 810 may house one or more components ofinformation handling system 700, for example one or more applicationprocessors 710, one or more of SDRAM 714, NAND flash 716, NOR flash 718,baseband processor 712, and/or WWAN transceiver 720. The informationhandling system 700 further may optionally include a physical actuatorarea 820 which may comprise a keyboard or buttons for controllinginformation handling system via one or more buttons or switches. Theinformation handling system 700 may also include a memory port or slot756 for receiving non-volatile memory such as flash memory, for examplein the form of a secure digital (SD) card or a subscriber identitymodule (SIM) card. Optionally, the information handling system 700 mayfurther include one or more speakers and/or microphones 824 and aconnection port 754 for connecting the information handling system 700to another electronic device, dock, display, battery charger, and so on.In addition, information handling system 700 may include a headphone orspeaker jack 828 and one or more cameras 736 on one or more sides of thehousing 810. It should be noted that the information handling system 700of FIG. 8 may include more or fewer elements than shown, in variousarrangements, and the scope of the claimed subject matter is not limitedin this respect.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware. Embodiments describedherein may be implemented into a system using any suitably configuredhardware and/or software.

Referring now to FIG. 9 , example components of a wireless device suchas User Equipment (UE) device 900 in accordance with one or moreembodiments will be discussed. In some embodiments, UE device 900 mayinclude application circuitry 902, baseband circuitry 904, RadioFrequency (RF) circuitry 906, front-end module (FEM) circuitry 908 andone or more antennas 910, coupled together at least as shown.

Application circuitry 902 may include one or more applicationprocessors. For example, application circuitry 902 may include circuitrysuch as, but not limited to, one or more single-core or multi-coreprocessors. The one or more processors may include any combination ofgeneral-purpose processors and dedicated processors, for examplegraphics processors, application processors, and so on. The processorsmay be coupled with and/or may include memory and/or storage and may beconfigured to execute instructions stored in the memory and/or storageto enable various applications and/or operating systems to run on thesystem.

Baseband circuitry 904 may include circuitry such as, but not limitedto, one or more single-core or multi-core processors. Baseband circuitry104 may include one or more baseband processors and/or control logic toprocess baseband signals received from a receive signal path of RFcircuitry 906 and to generate baseband signals for a transmit signalpath of the RF circuitry 906. Baseband processing circuitry 904 mayinterface with the application circuitry 902 for generation andprocessing of the baseband signals and for controlling operations of theRF circuitry 906. For example, in some embodiments, the basebandcircuitry 904 may include a second generation (2G) baseband processor904 a, third generation (3G) baseband processor 904 b, fourth generation(4G) baseband processor 904 c, and/or one or more other basebandprocessors 904 d for other existing generations, generations indevelopment or to be developed in the future, for example fifthgeneration (5G), sixth generation (6G), and so on. Baseband circuitry904, for example one or more of baseband processors 904 a through 904 d,may handle various radio control functions that enable communicationwith one or more radio networks via RF circuitry 906. The radio controlfunctions may include, but are not limited to, signal modulation and/ordemodulation, encoding and/or decoding, radio frequency shifting, and soon. In some embodiments, modulation and/or demodulation circuitry ofbaseband circuitry 904 may include Fast-Fourier Transform (FFT),precoding, and/or constellation mapping and/or demapping functionality.In some embodiments, encoding and/or decoding circuitry of basebandcircuitry 904 may include convolution, tail-biting convolution, turbo,Viterbi, and/or Low Density Parity Check (LDPC) encoder and/or decoderfunctionality. Embodiments of modulation and/or demodulation and encoderand/or decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, baseband circuitry 904 may include elements of aprotocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. Processor 904 e of the baseband circuitry 904may be configured to run elements of the protocol stack for signaling ofthe PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, thebaseband circuitry may include one or more audio digital signalprocessors (DSP) 904 f. The one or more audio DSPs 904 f may includeelements for compression and/or decompression and/or echo cancellationand may include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of baseband circuitry 904 and application circuitry 902 maybe implemented together such as, for example, on a system on a chip(SOC).

In some embodiments, baseband circuitry 904 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, baseband circuitry 904 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), a wireless personal area network(WPAN). Embodiments in which baseband circuitry 904 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 906 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, RF circuitry 906 may include switches, filters,amplifiers, and so on, to facilitate the communication with the wirelessnetwork. RF circuitry 906 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from FEM circuitry908 and provide baseband signals to baseband circuitry 904. RF circuitry906 may also include a transmit signal path which may include circuitryto up-convert baseband signals provided by the baseband circuitry 904and provide RF output signals to FEM circuitry 908 for transmission.

In some embodiments, RF circuitry 906 may include a receive signal pathand a transmit signal path. The receive signal path of RF circuitry 906may include mixer circuitry 906 a, amplifier circuitry 906 b and filtercircuitry 906 c. The transmit signal path of RF circuitry 906 mayinclude filter circuitry 906 c and mixer circuitry 906 a. RF circuitry906 may also include synthesizer circuitry 906 d for synthesizing afrequency for use by the mixer circuitry 106 a of the receive signalpath and the transmit signal path. In some embodiments, the mixercircuitry 906 a of the receive signal path may be configured todown-convert RF signals received from FEM circuitry 908 based on thesynthesized frequency provided by synthesizer circuitry 1906 d.Amplifier circuitry 906 b may be configured to amplify thedown-converted signals and the filter circuitry 906 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to baseband circuitry904 for further processing. In some embodiments, the output basebandsignals may be zero-frequency baseband signals, although this is not arequirement. In some embodiments, mixer circuitry 906 a of the receivesignal path may comprise passive mixers, although the scope of theembodiments is not limited in this respect.

In some embodiments, mixer circuitry 906 a of the transmit signal pathmay be configured to up-convert input baseband signals based on thesynthesized frequency provided by synthesizer circuitry 906 d togenerate RF output signals for FEM circuitry 908. The baseband signalsmay be provided by the baseband circuitry 904 and may be filtered byfilter circuitry 906 c. Filter circuitry 906 c may include a low-passfilter (LPF), although the scope of the embodiments is not limited inthis respect.

In some embodiments, mixer circuitry 906 a of the receive signal pathand the mixer circuitry 906 a of the transmit signal path may includetwo or more mixers and may be arranged for quadrature down conversionand/or up conversion respectively. In some embodiments, mixer circuitry906 a of the receive signal path and the mixer circuitry 906 a of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection, for example Hartley image rejection. In someembodiments, mixer circuitry 906 a of the receive signal path and themixer circuitry 906 a may be arranged for direct down conversion and/ordirect up conversion, respectively. In some embodiments, mixer circuitry906 a of the receive signal path and mixer circuitry 906 a of thetransmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, RFcircuitry 906 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry, and baseband circuitry 904may include a digital baseband interface to communicate with RFcircuitry 906. In some dual-mode embodiments, separate radio integratedcircuit (IC) circuitry may be provided for processing signals for one ormore spectra, although the scope of the embodiments is not limited inthis respect.

In some embodiments, synthesizer circuitry 906 d may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theembodiments is not limited in this respect as other types of frequencysynthesizers may be suitable. For example, synthesizer circuitry 906 dmay be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

Synthesizer circuitry 106 d may be configured to synthesize an outputfrequency for use by mixer circuitry 906 a of RF circuitry 906 based ona frequency input and a divider control input. In some embodiments,synthesizer circuitry 906 d may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either baseband circuitry 904 orapplications processor 902 depending on the desired output frequency. Insome embodiments, a divider control input (e.g., N) may be determinedfrom a look-up table based on a channel indicated by applicationsprocessor 902.

Synthesizer circuitry 906 d of RF circuitry 906 may include a divider, adelay-locked loop (DLL), a multiplexer and a phase accumulator. In someembodiments, the divider may be a dual modulus divider (DMD) and thephase accumulator may be a digital phase accumulator (DPA). In someembodiments, the DMD may be configured to divide the input signal byeither N or N+1, for example based on a carry out, to provide afractional division ratio. In some example embodiments, the DLL mayinclude a set of cascaded, tunable, delay elements, a phase detector, acharge pump and a D-type flip-flop. In these embodiments, the delayelements may be configured to break a VCO period up into Nd equalpackets of phase, where Nd is the number of delay elements in the delayline. In this way, the DLL provides negative feedback to help ensurethat the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 906 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency, for example twice the carrier frequency, four times thecarrier frequency, and so on, and used in conjunction with quadraturegenerator and divider circuitry to generate multiple signals at thecarrier frequency with multiple different phases with respect to eachother. In some embodiments, the output frequency may be a localoscillator (LO) frequency (fLO). In some embodiments, RF circuitry 906may include an in-phase and quadrature (IQ) and/or polar converter.

FEM circuitry 908 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 910, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 906 for furtherprocessing. FEM circuitry 908 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by RF circuitry 906 for transmission by one ormore of the one or more antennas 910.

In some embodiments, FEM circuitry 908 may include a transmit/receive(TX/RX) switch to switch between transmit mode and receive modeoperation. FEM circuitry 908 may include a receive signal path and atransmit signal path. The receive signal path of FEM circuitry 908 mayinclude a low-noise amplifier (LNA) to amplify received RF signals andto provide the amplified received RF signals as an output, for exampleto RF circuitry 906. The transmit signal path of FEM circuitry 908 mayinclude a power amplifier (PA) to amplify input RF signals, for exampleprovided by RF circuitry 906, and one or more filters to generate RFsignals for subsequent transmission, for example by one or more ofantennas 910. In some embodiments, UE device 900 may include additionalelements such as, for example, memory and/or storage, display, camera,sensor, and/or input/output (I/O) interface, although the scope of theclaimed subject matter is not limited in this respect.

In a first example, an information handling system to manage resourcesin a network having a mobility management entity (MME) pool to performload balancing comprises circuitry configured to receive performancemeasurements for at least one MME in the MME pool, if at least one ofthe performance measurements exceeds at least one predeterminedthreshold, request to instantiate a new mobility management entityvirtual network function (MME VNF), instantiate the MME VNF in responseto the request, and connect one or more user equipment (UE) devicesmanaged by the MME pool to the added MME VNF.

In a second example, an information handling system to manage resourcesin a network having a mobility management entity (MME) pool to performload balancing comprises circuitry configured to receive performancemeasurements of an MME virtual network function (MME VNF), if at leastone of the performance measurements exceeds at least one predeterminedthreshold, send a request to scale out a new MME VNF, instantiate thenew MME VNF in response to the request, and connect one or more userequipment (UE) devices managed by the MME pool to the new MME VNF.

In a third example, an information handling system to manage resourcesin a network having a mobility management entity (MME) pool comprisescircuitry configured to receive performance measurements of an MMEvirtual network function (MME VNF), if at least one of the performancemeasurements exceeds at least one predetermined threshold, send arequest to scale up MME VNF resources, increase the MME VNF resources inresponse to the request, and update one or more user equipment (UE)devices managed by the MME pool with a new weight factor according tothe increased MME VNF resources.

In a fourth example, an information handling system to manage resourcesin a network having a mobility management entity (MME) pool to performload balancing comprises circuitry configured to receive performancemeasurements of an MME virtual network function (MME VNF), if at leastone of the performance measurements is below at least one predeterminedthreshold, send a request to scale in the MME VNF, offload one or moreuser equipment (UE) devices managed by the MME pool to a different MMEVNF, and terminate the MME VNF to be scaled in.

In a fifth example, an information handling system to manage resourcesin a network having a mobility management entity (MME) pool comprisescircuitry configured to receive performance measurements of an MMEvirtual network function (MME VNF), if at least one of the performancemeasurements is below at least one predetermined threshold, send arequest to scale down MME VNF resources, decrease the MME VNF resourcesin response to the request, and update one or more user equipment (UE)devices managed by the MME pool with a new weight factor according tothe increased MME VNF resources.

In a sixth example, a method to manage resources in a network having amobility management entity (MME) pool to perform load balancingcomprises receiving performance measurements for at least one MME in theMME pool, if at least one of the performance measurements exceeds atleast one predetermined threshold, requesting to instantiate a newmobility management entity virtual network function (MME VNF),instantiating the MME VNF in response to the request, and connecting oneor more user equipment (UE) devices managed by the MME pool to the addedMME VNF.

In a seventh example, a method to manage resources in a network having amobility management entity (MME) pool to perform load balancingcomprises receiving performance measurements of an MME virtual networkfunction (MME VNF), if at least one of the performance measurementsexceeds at least one predetermined threshold, sending a request to scaleout a new MME VNF, instantiating the new MME VNF in response to therequest, and connecting one or more user equipment (UE) devices managedby the MME pool to the new MME VNF.

In an eighth example, a method to manage resources in a network having amobility management entity (MME) pool comprises receiving performancemeasurements of an MME virtual network function (MME VNF), if at leastone of the performance measurements exceeds at least one predeterminedthreshold, sending a request to scale up MME VNF resources, increasingthe MME VNF resources in response to the request, and updating one ormore user equipment (UE) devices managed by the MME pool with a newweight factor according to the increased MME VNF resources.

In a ninth example, a method to manage resources in a network having amobility management entity (MME) pool to perform load balancingcomprises receiving performance measurements of an MME virtual networkfunction (MME VNF), if at least one of the performance measurements isbelow at least one predetermined threshold, sending a request to scalein the MME VNF, offloading one or more user equipment (UE) devicesmanaged by the MME pool to a different MME VNF, and terminating the MMEVNF to be scaled in.

In a tenth example, a method to manage resources in a network having amobility management entity (MME) pool comprises receiving performancemeasurements of an MME virtual network function (MME VNF), if at leastone of the performance measurements is below at least one predeterminedthreshold, sending a request to scale down MME VNF resources, decreasingthe MME VNF resources in response to the request, and updating one ormore user equipment (UE) devices managed by the MME pool with a newweight factor according to the increased MME VNF resources.

In an eleventh example, an article of manufacture comprising anon-transitory storage medium having instructions stored thereon tomanage resources in a network having a mobility management entity (MME)pool to perform load balancing, wherein the instructions, if executed,result in receiving performance measurements for at least one MME in theMME pool, if at least one of the performance measurements exceeds atleast one predetermined threshold, requesting to instantiate a newmobility management entity virtual network function (MME VNF),instantiating the MME VNF in response to the request, and connecting oneor more user equipment (UE) devices managed by the MME pool to the addedMME VNF.

In a twelfth example, an article of manufacture comprising anon-transitory storage medium having instructions stored thereon tomanage resources in a network having a mobility management entity (MME)pool to perform load balancing, wherein the instructions, if executed,result in receiving performance measurements of an MME virtual networkfunction (MME VNF), if at least one of the performance measurementsexceeds at least one predetermined threshold, sending a request to scaleout a new MME VNF, instantiating the new MME VNF in response to therequest, and connecting one or more user equipment (UE) devices managedby the MME pool to the new MME VNF.

In a thirteenth example, an article of manufacture comprising anon-transitory storage medium having instructions stored thereon tomanage resources in a network having a mobility management entity (MME)pool to perform load balancing, wherein the instructions, if executed,result in receiving performance measurements of an MME virtual networkfunction (MME VNF), if at least one of the performance measurementsexceeds at least one predetermined threshold, sending a request to scaleup MME VNF resources, increasing the MME VNF resources in response tothe request, and updating one or more user equipment (UE) devicesmanaged by the MME pool with a new weight factor according to theincreased MME VNF resources.

In a fourteenth example, an article of manufacture comprising anon-transitory storage medium having instructions stored thereon tomanage resources in a network having a mobility management entity (MME)pool to perform load balancing, wherein the instructions, if executed,result in receiving performance measurements of an MME virtual networkfunction (MME VNF), if at least one of the performance measurements isbelow at least one predetermined threshold, sending a request to scalein the MME VNF, offloading one or more user equipment (UE) devicesmanaged by the MME pool to a different MME VNF, and terminating the MMEVNF to be scaled in.

In a fifteenth example, an article of manufacture comprising anon-transitory storage medium having instructions stored thereon tomanage resources in a network having a mobility management entity (MME)pool to perform load balancing, wherein the instructions, if executed,result in receiving performance measurements of an MME virtual networkfunction (MME VNF), if at least one of the performance measurements isbelow at least one predetermined threshold, sending a request to scaledown MME VNF resources, decreasing the MME VNF resources in response tothe request, and updating one or more user equipment (UE) devicesmanaged by the MME pool with a new weight factor according to theincreased MME VNF resources.

In some of the above examples, the following further examples may apply.The performance measurements are received from a monitor function in theat least one MME. The performance measurements comprise MME processorusage, the circuitry being further configured to allocate additionalcomputing or storing resources, or a combination thereof, if an MMEprocessor usage counter exceeds a threshold value. The performancemeasurements comprise S1-MME data volume, and the circuitry is furtherconfigured to add networking capacity if an S1-MME data counter exceedsa threshold value. The performance measurements are received by anetwork manager (NM) for the network, and the NM determines if at leastone of the performance measurements exceeds at least one predeterminedthreshold. The performance measurements are received by a networkmanager (NM) for the network, the NM forwards the load measurements to anetwork virtual functions orchestrator (NFV orchestrator), and the NFVorchestrator determines if at least one of the performance measurementsexceeds at least one predetermined threshold. The performancemeasurements are received by a VNF manager for the network, and the VNFmanager determines if at least one of the performance measurementsexceeds at least one predetermined threshold. The performancemeasurements are received by a VNF manager for the network, the VNFmanager forwards the load measurements to a network virtual functionsorchestrator (NFV orchestrator), and the NFV orchestrator determines ifat least one of the performance measurements exceeds at least onepredetermined threshold. The performance measurements are received by anelement manager for the network, and the element manager determines ifat least one of the performance measurements exceeds at least onepredetermined threshold. The performance measurements are received by anelement manager for the network, the element manager forwards the loadmeasurements to a network virtual functions orchestrator (NFVorchestrator), via VNFM, and the NFV orchestrator determines if at leastone of the performance measurements exceeds at least one predeterminedthreshold. The MME pool comprises at least one physical MME networkelement, and said connecting comprises rebalancing one or more UEs fromthe physical MME network element to the MME VNF. The circuitry isfurther configured to terminate the MME VNF if at least one of theperformance measurements falls below at least one predeterminedthreshold.

In some of the above examples, the following further examples may apply.The performance measurements are received from a monitor function in theat least one MME VNF. The performance measurements comprise MMEprocessor usage, and the circuitry is further configured to removecomputing or storing resources, or a combination thereof, if an MMEprocessor usage counter is below a threshold value. The loadmeasurements comprise S1-MME data volume, and the circuitry is furtherconfigured to remove networking capacity if an S1-MME data counter isbelow a threshold value. The performance measurements are received by anetwork manager (NM) for the network, and the NM determines if the leastone of the performance measurements is below at least one predeterminedthreshold. The performance measurements are received by a networkmanager (NM) for the network, the NM forwards the load measurements to anetwork virtual functions orchestrator (NVF orchestrator), and the NFVorchestrator determines if the least one of the performance measurementsis below at least one predetermined threshold. The performancemeasurements are received by a VNF manager for the network, and the VNFmanager determines if at least one of the performance measurements isbelow at least one predetermined threshold. The performance measurementsare received by a VNF manager for the network, the VNF manager forwardsthe load measurements to a network virtual functions orchestrator (NVForchestrator), and the NFV orchestrator determines if at least one ofthe performance measurements is below at least one predeterminedthreshold. The performance measurements are received by an elementmanager for the network, and the element manager determines if at leastone of the performance measurements is below at least one predeterminedthreshold. The performance measurements are received by an elementmanager for the network, the element manager forwards the loadmeasurements to a network virtual functions orchestrator (NVForchestrator), and the NFV orchestrator determines if at least one ofthe performance measurements is below at least one predeterminedthreshold.

Although the claimed subject matter has been described with a certaindegree of particularity, it should be recognized that elements thereofmay be altered by persons skilled in the art without departing from thespirit and/or scope of claimed subject matter. It is believed that thesubject matter pertaining to virtualized network function management andmany of its attendant utilities will be understood by the forgoingdescription, and it will be apparent that various changes may be made inthe form, construction and/or arrangement of the components thereofwithout departing from the scope and/or spirit of the claimed subjectmatter or without sacrificing all of its material advantages, the formherein before described being merely an explanatory embodiment thereof,and/or further without providing substantial change thereto. It is theintention of the claims to encompass and/or include such changes.

What is claimed is:
 1. An information handling system to manageresources in a network having a mobility management entity (MME) pool toperform load balancing, comprising circuitry configured to: receiveperformance measurements for at least one MME in the MME pool, whereinthe performance measurements are received by a network manager (NM) forthe network, VNF manager for the network, or an element manager for thenetwork; forward the performance measurements from a network functionsvirtualization network manager (NFV NM) to a network virtual functionsorchestrator (NFV orchestrator) to allow the NFV orchestrator todetermine if at least one of the performance measurements exceeds atleast one predetermined threshold; if the NFV orchestrator determinesthat at least one of the performance measurements exceeds at least onepredetermined threshold, receive a request from the NFV orchestrator toinstantiate a new mobility management entity virtual network function(MME VNF); instantiate the new MME VNF in response to the request; andconnect one or more user equipment (UE) devices managed by the MME poolto the new MME VNF.
 2. The information handling system as claimed inclaim 1, wherein the performance measurements comprise MME processorusage or S1-MME data volume, the circuitry being further configured toallocate additional computing or storing resources, or a combinationthereof, if an MME processor usage counter or an S1-MME data counterexceeds a threshold value.
 3. The information handling system as claimedin claim 1, wherein the MME pool comprises at least one physical MMEnetwork element, and the circuitry is further configured to rebalanceone or more UEs from the physical MME network element to the MME VNF. 4.The information handling system as claimed in claim 1, wherein thecircuitry is further configured to terminate the MME VNF if at least oneof the performance measurements falls below at least one predeterminedthreshold.
 5. An information handling system to manage resources in anetwork having a mobility management entity (MME) pool to perform loadbalancing, comprising circuitry configured to: receive performancemeasurements for at least one MME in the MME pool, wherein theperformance measurements are received by a network manager (NM) for thenetwork, VNF manager for the network, or an element manager for thenetwork; forward the performance measurements from a network functionsvirtualization network manager (NFV NM) to a network virtual functionsorchestrator (NFV orchestrator) to allow the NFV orchestrator todetermine if at least one of the performance measurements exceeds atleast one predetermined threshold; if the NFV orchestrator determinesthat at least one of the performance measurements exceeds at least onepredetermined threshold, send a request to scale out a new MME VNF;instantiate the new MME VNF in response to the request; and connect oneor more user equipment (UE) devices managed by the MME pool to the newMME VNF.
 6. The information handling system as claimed in claim 5,wherein the performance measurements comprise MME processor usage orS1-MME data volume, the circuitry being further configured to allocateadditional computing or storing resources, or a combination thereof, ifan MME processor usage counter or an S1-MME data counter exceeds athreshold value.
 7. The information handling system as claimed in claim5, wherein the MME pool comprises at least one physical MME networkelement, and the circuitry is further configured to rebalance one ormore UEs from the physical MME network element to the MME VNF.
 8. Theinformation handling system as claimed in claim 5, wherein the circuitryis further configured to: send a request to scale in the MME VNF if atleast one of the performance measurements is below at least onepredetermined threshold; offload one or more user equipment (UE) devicesmanaged by the MME pool to a different MME VNF; and terminate the MMEVNF to be scaled in.
 9. An article of manufacture comprising anon-transitory storage medium having instructions stored thereon tomanage resources in a network having a mobility management entity (MME)pool to perform load balancing, wherein the instructions, if executed bya processor, result in: receive performance measurements for at leastone MME in the MME pool, wherein the performance measurements arereceived by a network manager (NM) for the network, VNF manager for thenetwork, or an element manager for the network; forwarding theperformance measurements from a network functions virtualization networkmanager (NFV NM) to a network virtual functions orchestrator (NFVorchestrator) to allow the NFV orchestrator to determine if at least oneof the performance measurements exceeds at least one predeterminedthreshold; if the NFV orchestrator determines that at least one of theperformance measurements exceeds at least one predetermined threshold,requesting to instantiate a new mobility management entity virtualnetwork function (MME VNF); instantiating the MME VNF in response to therequest; and connecting one or more user equipment (UE) devices managedby the MME pool to the added MME VNF.
 10. The article of manufacture asclaimed in claim 9, wherein the performance measurements comprise MMEprocessor usage or S1-MME data volume, the instructions furtherresulting in allocating additional computing or storing resources, or acombination thereof, if an MME processor usage counter or an S1-MME datacounter exceeds a threshold value.
 11. The article of manufacture asclaimed in claim 9, wherein the MME pool comprises at least one physicalMME network element, and the method further comprises rebalancing one ormore UEs from the physical MME network element to the MME VNF.
 12. Thearticle of manufacture as claimed in claim 9, wherein the instructions,if executed, further result in terminating the MME VNF if at least oneof the performance measurements falls below at least one predeterminedthreshold.
 13. An article of manufacture comprising a non-transitorystorage medium having instructions stored thereon to manage resources ina network having a mobility management entity (MME) pool to perform loadbalancing, wherein the instructions, if executed by a processor, resultin: receive performance measurements for at least one MME in the MMEpool, wherein the performance measurements are received by a networkmanager (NM) for the network, VNF manager for the network, or an elementmanager for the network; forwarding the performance measurements from anetwork functions virtualization network manager (NFV NM) to a networkvirtual functions orchestrator (NFV orchestrator) to allow the NFVorchestrator to determine if at least one of the performancemeasurements exceeds at least one predetermined threshold; if the NFVorchestrator determines at least one of the performance measurementsexceeds at least one predetermined threshold, sending a request to scaleout a new MME VNF; instantiating the new MME VNF in response to therequest; and connecting one or more user equipment (UE) devices managedby the MME pool to the new MME VNF.
 14. The article of manufacture asclaimed in claim 13, wherein the performance measurements comprise MMEprocessor usage or S1-MME data volume, the instructions furtherresulting in allocating additional computing or storing resources, or acombination thereof, if an MME processor usage counter or an S1-MME datacounter exceeds a threshold value.